-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OCPBUGS-42483: PowerVS: update capi ibmcloud c6bcd313 for 4.17 #9054
OCPBUGS-42483: PowerVS: update capi ibmcloud c6bcd313 for 4.17 #9054
Conversation
@hamzy: This pull request references Jira Issue OCPBUGS-42483, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
/jira refresh |
@hamzy: This pull request references Jira Issue OCPBUGS-42483, which is valid. The bug has been moved to the POST state. 7 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
/assign @r4f4 |
k8s.io/cloud-provider-vsphere v1.30.1 | ||
k8s.io/klog v1.0.0 | ||
k8s.io/klog/v2 v2.120.1 | ||
k8s.io/utils v0.0.0-20240310230437-4693a0247e57 | ||
libvirt.org/go/libvirtxml v1.10002.0 | ||
sigs.k8s.io/cluster-api v1.7.3 | ||
sigs.k8s.io/cluster-api v1.8.2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should also bump the capi binary to the same version in cluster-api/cluster-api
. Building against one version and running another is asking for trouble.
When we bump, we need to make sure all the other providers still work, so this PR needs to be thoroughly tested.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@r4f4 Updated...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see the update. Maybe you forgot to push the new commit?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Weird. It is here locally and was pushed.
hamzy:hamzy-installer$ grep 'sigs.k8s.io/cluster-api v1.8.2' go.mod
sigs.k8s.io/cluster-api v1.8.2
hamzy:hamzy-installer$ git status
On branch PowerVS-Update-417-CAPI-ibmcloud-c6bcd313
Your branch is up to date with 'origin/PowerVS-Update-417-CAPI-ibmcloud-c6bcd313'.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Forgot to also modify cluster-api/cluster-api/go.mod
:(
Thanks!
8a3cf7b
to
8536700
Compare
8536700
to
6240605
Compare
/retest-required |
/hold Let's fix the capi mismatch in the master branch first. |
/test e2e-powervs-ovn |
Fix proposed in #9055 |
/test e2e-ibmcloud-ovn |
/test e2e-powervs-ovn |
@hamzy: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
/hold cancel |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: r4f4 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@gpei Hello, could you please label cherry-pick-approved? |
/test e2e-openstack-ovn e2e-vsphere-ovn e2e-nutanix-ovn |
/label backport-risk-assessed |
/lgtm |
/label cherry-pick-approved |
a1b46a5
into
openshift:release-4.17
@hamzy: Jira Issue OCPBUGS-42483: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-42483 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
[ART PR BUILD NOTIFIER] Distgit: ose-installer-altinfra |
[ART PR BUILD NOTIFIER] Distgit: ose-baremetal-installer |
[ART PR BUILD NOTIFIER] Distgit: ose-installer-terraform-providers |
[ART PR BUILD NOTIFIER] Distgit: ose-installer-artifacts |
Update the installer to use commit c6bcd313bce0fc9866e41bb9e3487d9f61c628a3 of cluster-api-provider-ibmcloud
This includes a couple of necessary Transit Gateway fixes.